This looks fine to me, @ddobrin please confirm

I have reviewed both light-rest-4j and json-schema-validator as they are related changes. In general I am OK with the change but there might be small improvements to the code base.

• I think we should keep the ValidatorConfig in light-rest-4j and change the json-schema-validator config to something like SchemaValidatorConfig. As we have config file in light-rest-4j named validator.yml and it matches to ValidatorConfig class as others. It is very hard to change the config file name in light-rest-4j as there are a lot of users. However, it is very easy to change the config file name in json-shema-validator as it is an underline library and nobody cares about.

• Any reason you have fixed user-invalid-malformatedjson.json? It is created for a negative test and it is not a valid json as the last curly brace is missing.

Thanks a lot for the effort. It is a very big change.

Thank you for reviewing.

I think we should keep the ValidatorConfig in light-rest-4j and change the json-schema-validator config to something like SchemaValidatorConfig. As we have config file in light-rest-4j named validator.yml and it matches to ValidatorConfig class as others. It is very hard to change the config file name in light-rest-4j as there are a lot of users. However, it is very easy to change the config file name in json-shema-validator as it is an underline library and nobody cares about.

I get your point, I'll change the config in json-schema-validator instead of in light-rest-4j.

Any reason you have fixed user-invalid-malformatedjson.json? It is created for a negative test and it is not a valid json as the last curly brace is missing.

Sorry, I didn't pay attention the file name, I thought it's a typo missing "}", I'll change it back.